Problem

It's nice if single query : single response :: batch query : batch response.

But at present, in the single case we send { query: '', params: [] } and get back a single { rows: [], ... } object, while in the batch case we send an array of { query: '', params: [] } objects and get back not an array of { rows: [], ... } objects but a { results: [ { rows: [] , ... }, { rows: [] , ... }, ... ] } object instead.

Summary of changes

With this change, the batch query body becomes { queries: [{ query: '', params: [] }, ... ] }, which restores a consistent relationship between the request and response bodies.

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.
• Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
• If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

• Do not forget to reformat commit message to not include the above checklist